Skip to content

tls: introduce secureContext for tls.connect#8959

Closed
indutny wants to merge 1 commit into
nodejs:v4.x-stagingfrom
indutny:backport/c5b4f6bc996e25f9e24db8ed31df86010d2dfcec
Closed

tls: introduce secureContext for tls.connect#8959
indutny wants to merge 1 commit into
nodejs:v4.x-stagingfrom
indutny:backport/c5b4f6bc996e25f9e24db8ed31df86010d2dfcec

Conversation

@indutny

@indutny indutny commented Oct 6, 2016

Copy link
Copy Markdown
Member
Checklist
  • make -j8 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

tls

Description of change

Add secureContext option to tls.connect. It is useful for caching
client certificates, key, and CA certificates.

PR-URL: #4246
Reviewed-By: James M Snell jasnell@gmail.com


Backport of: #4246 (comment)

@nodejs-github-bot nodejs-github-bot added tls Issues and PRs related to the tls subsystem. v4.x labels Oct 6, 2016
@indutny

indutny commented Oct 6, 2016

Copy link
Copy Markdown
Member Author

cc @thealphanerd

@indutny

indutny commented Oct 6, 2016

Copy link
Copy Markdown
Member Author

@MylesBorins MylesBorins added the semver-minor PRs that contain new features and should be released in the next minor version. label Oct 6, 2016
@MylesBorins MylesBorins self-assigned this Oct 6, 2016

@jasnell jasnell left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@MylesBorins MylesBorins force-pushed the v4.x-staging branch 2 times, most recently from 6a126fb to 004d665 Compare October 10, 2016 22:18
@indutny

indutny commented Oct 23, 2016

Copy link
Copy Markdown
Member Author

@thealphanerd should it be landed?

@jasnell

jasnell commented Oct 23, 2016

Copy link
Copy Markdown
Member

Looks like this needs to be rebased.

@MylesBorins MylesBorins added this to the v4.7.0 milestone Oct 24, 2016
Add `secureContext` option to `tls.connect`. It is useful for caching
client certificates, key, and CA certificates.

PR-URL: nodejs#4246
Reviewed-By: James M Snell <jasnell@gmail.com>
@indutny indutny force-pushed the backport/c5b4f6bc996e25f9e24db8ed31df86010d2dfcec branch from 22d7fc6 to 125977b Compare October 24, 2016 18:38
@indutny

indutny commented Oct 24, 2016

Copy link
Copy Markdown
Member Author

@jasnell Voila! Though, there were no conflict 😉 This PR will become stale again unless we'll land it. cc @thealphanerd

@jasnell

jasnell commented Oct 26, 2016

Copy link
Copy Markdown
Member

I'm good for this to land.

@indutny

indutny commented Oct 27, 2016

Copy link
Copy Markdown
Member Author

@thealphanerd should I just land it? How does it work?

@MylesBorins

Copy link
Copy Markdown
Contributor

you can land it on staging 😊

@indutny

indutny commented Oct 27, 2016

Copy link
Copy Markdown
Member Author

Landed in d9b5437, thank you!

@indutny indutny closed this Oct 27, 2016
@indutny indutny deleted the backport/c5b4f6bc996e25f9e24db8ed31df86010d2dfcec branch October 27, 2016 00:55
@MylesBorins MylesBorins removed this from the 4.7.0 milestone Nov 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver-minor PRs that contain new features and should be released in the next minor version. tls Issues and PRs related to the tls subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants